chore: bump version to 1.6.0#23
Merged
Merged
Conversation
Cuts the [1.6.0] release: - Per-endpoint circuit breaker option (`per_endpoint_circuit_breaker`, `breaker_key_fn`) on `HyperpingClient` and `AsyncHyperpingClient`. Non-breaking; defaults preserve the previous single-shared-breaker behaviour.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cuts the 1.6.0 release. Non-breaking, minor bump.
Included since 1.5.0
per_endpoint_circuit_breaker: bool = False) onHyperpingClientandAsyncHyperpingClient(feat: per-endpoint circuit breaker option #22). Sub-resource paths bucket under their parentEndpointprefix so the breaker set stays bounded. Custom bucketing viabreaker_key_fn. State for any path readable viaclient.circuit_breaker_state_for(path)in either mode.SECURITY.md— published vulnerability-reporting policy (docs: add SECURITY.md #21).Defaults are preserved: existing callers see no behaviour change.
Release steps after merge
v1.6.0onmainand push the tag.publish.ymlworkflow (triggered onv*tags) builds and publishes to PyPI.Test plan
uv syncproduces matchinguv.lockpython -c "import hyperping; print(hyperping.__version__)"reports1.6.0